Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60127e08b1139a97f8f6f43957fddd77b4276dd9f4aa37b6af6545c40b346efc

Tx prefix hash: 6822c58a6e3c4eaca5a5254f11ca6fa67a045af9849d17053e619d4d1bb94a2d
Tx public key: 0676a1b8a11fa3cf46556ceaf6c60b19dd1c6a3b41687fcb01c9591e8d33f237
Timestamp: 1745012545 Timestamp [UCT]: 2025-04-18 21:42:25 Age [y:d:h:m:s]: 00:025:19:04:18
Block: 1264423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18450 RingCT/type: yes/0
Extra: 010676a1b8a11fa3cf46556ceaf6c60b19dd1c6a3b41687fcb01c9591e8d33f2370211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0be203e3fbc96750ad8fadaa617637b22356829d221f57d1ad97f9d0e9950448 0.600000000000 1751620 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": 1264433, "vin": [ { "gen": { "height": 1264423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0be203e3fbc96750ad8fadaa617637b22356829d221f57d1ad97f9d0e9950448" } } ], "extra": [ 1, 6, 118, 161, 184, 161, 31, 163, 207, 70, 85, 108, 234, 246, 198, 11, 25, 221, 28, 106, 59, 65, 104, 127, 203, 1, 201, 89, 30, 141, 51, 242, 55, 2, 17, 0, 0, 0, 1, 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