Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0c96d319eed9eeb6ab99411e16fbd56835be28c6522c1d757d3350d622d3ee5d

Tx prefix hash: 437a41c92b0298120ed1def3fceacc8533c38cc071ac42aa3a28a45cd82a8d20
Tx public key: 8e4e723f82d926d973ad3f3848f35bed03fe028c6630ab0c61b381830e09aafb
Timestamp: 1675013728 Timestamp [UCT]: 2023-01-29 17:35:28 Age [y:d:h:m:s]: 02:253:12:33:35
Block: 685492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 700485 RingCT/type: yes/0
Extra: 018e4e723f82d926d973ad3f3848f35bed03fe028c6630ab0c61b381830e09aafb021100000013835e4d22000000000000000000

1 output(s) for total of 3.286096987000 dcy

stealth address amount amount idx
00: acb6335345a488b8c999f1dd3d941e9b66c7dad1cc414c307cf01ea6be96b86c 3.286096987000 1127823 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 685502, "vin": [ { "gen": { "height": 685492 } } ], "vout": [ { "amount": 3286096987, "target": { "key": "acb6335345a488b8c999f1dd3d941e9b66c7dad1cc414c307cf01ea6be96b86c" } } ], "extra": [ 1, 142, 78, 114, 63, 130, 217, 38, 217, 115, 173, 63, 56, 72, 243, 91, 237, 3, 254, 2, 140, 102, 48, 171, 12, 97, 179, 129, 131, 14, 9, 170, 251, 2, 17, 0, 0, 0, 19, 131, 94, 77, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8