Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef6ebb11ff4a2c8330158c0280548b746b62426e1cc87d2cb5e680c3d394950f

Tx prefix hash: 767c1d6b6f974c1b84cd66a2ca1dd75e0267e72a1d727a9c11da453f407c187d
Tx public key: c7e8207ab12f8997246f00d62caafcd403f2ab6d322e801d8646d1ca2b542452
Timestamp: 1759240453 Timestamp [UCT]: 2025-09-30 13:54:13 Age [y:d:h:m:s]: 00:045:06:46:10
Block: 1379760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32433 RingCT/type: yes/0
Extra: 01c7e8207ab12f8997246f00d62caafcd403f2ab6d322e801d8646d1ca2b542452021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 717a88ff652f6bde70134c9473db7e3a6fd3a82a1ab1890539f63d691e702bcc 0.600000000000 1867867 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": 1379770, "vin": [ { "gen": { "height": 1379760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "717a88ff652f6bde70134c9473db7e3a6fd3a82a1ab1890539f63d691e702bcc" } } ], "extra": [ 1, 199, 232, 32, 122, 177, 47, 137, 151, 36, 111, 0, 214, 44, 170, 252, 212, 3, 242, 171, 109, 50, 46, 128, 29, 134, 70, 209, 202, 43, 84, 36, 82, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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