Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2720a93323951b0c089de624c8a96e8e2021f74332e301e3bdd4b82f40a4cea7

Tx prefix hash: 6089371b34fb89c5ee3ba3115c1b69cb5142a44d604a14b6a79f679e1d86d9d3
Tx public key: f8a99c9c2cabbe8e9445a691aa4c6f5a70187b275b0ecd8d196e1abba70747d7
Timestamp: 1761573124 Timestamp [UCT]: 2025-10-27 13:52:04 Age [y:d:h:m:s]: 00:071:22:13:40
Block: 1399107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51499 RingCT/type: yes/0
Extra: 01f8a99c9c2cabbe8e9445a691aa4c6f5a70187b275b0ecd8d196e1abba70747d70211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26ed5a649063fe9ed2946740e3574f1500a0f2a0e8484cab9e470e0a94daf881 0.600000000000 1887412 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": 1399117, "vin": [ { "gen": { "height": 1399107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26ed5a649063fe9ed2946740e3574f1500a0f2a0e8484cab9e470e0a94daf881" } } ], "extra": [ 1, 248, 169, 156, 156, 44, 171, 190, 142, 148, 69, 166, 145, 170, 76, 111, 90, 112, 24, 123, 39, 91, 14, 205, 141, 25, 110, 26, 187, 167, 7, 71, 215, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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