Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0afe117fc88052c728590411d52db26f6ad63fc1ef541b087e34a74930a621a6

Tx prefix hash: 55c3628f34184201718ea9addf190892a35c20e5529302068cc1f758a35759d1
Tx public key: 29dae86409d49cc53a423ea7278c6d4808d6a6b6ee98c09e268f7e2ba6a8950f
Timestamp: 1712962010 Timestamp [UCT]: 2024-04-12 22:46:50 Age [y:d:h:m:s]: 01:013:21:53:18
Block: 999183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270926 RingCT/type: yes/0
Extra: 0129dae86409d49cc53a423ea7278c6d4808d6a6b6ee98c09e268f7e2ba6a8950f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec5625a9dc2bb45ea0146266739cfa9751bbf3c7c2738062a6d94d4c45df35e6 0.600000000000 1459661 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": 999193, "vin": [ { "gen": { "height": 999183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec5625a9dc2bb45ea0146266739cfa9751bbf3c7c2738062a6d94d4c45df35e6" } } ], "extra": [ 1, 41, 218, 232, 100, 9, 212, 156, 197, 58, 66, 62, 167, 39, 140, 109, 72, 8, 214, 166, 182, 238, 152, 192, 158, 38, 143, 126, 43, 166, 168, 149, 15, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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