Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86feb641356e6a7571d55f5e9ffca53b5adce4925cce2ad7df46787ab049b4c3

Tx prefix hash: ee7c4ff1faeb60924a516954f6ce36ed6fc93c12ede907df866141f723f9ea45
Tx public key: ad1bf41f0f1a4bd5f3cb8c3cd6ba9e0543657417a9a4e2580f644ea6781495cd
Timestamp: 1740845882 Timestamp [UCT]: 2025-03-01 16:18:02 Age [y:d:h:m:s]: 00:265:03:00:45
Block: 1229917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187239 RingCT/type: yes/0
Extra: 01ad1bf41f0f1a4bd5f3cb8c3cd6ba9e0543657417a9a4e2580f644ea6781495cd021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 941fc37b89981e9f829aa34efdfcc40102f0000983198045fda839f4a19343ea 0.600000000000 1716808 of 15

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": 1229927, "vin": [ { "gen": { "height": 1229917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "941fc37b89981e9f829aa34efdfcc40102f0000983198045fda839f4a19343ea" } } ], "extra": [ 1, 173, 27, 244, 31, 15, 26, 75, 213, 243, 203, 140, 60, 214, 186, 158, 5, 67, 101, 116, 23, 169, 164, 226, 88, 15, 100, 78, 166, 120, 20, 149, 205, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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