Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc853d2bbdb83f21a3b1a7f7a38559d7c5e0890ac97509fa8db70a246438b33d

Tx prefix hash: 6f6c0380d123695d9556af121e062a361fedc27463482a1c00bf3b6e512fc425
Tx public key: 129b56714c1d1fcadf1752b68262ed2b896836a32d12d211ce18520dfa42ef7c
Timestamp: 1712663388 Timestamp [UCT]: 2024-04-09 11:49:48 Age [y:d:h:m:s]: 00:165:05:26:36
Block: 996707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118376 RingCT/type: yes/0
Extra: 01129b56714c1d1fcadf1752b68262ed2b896836a32d12d211ce18520dfa42ef7c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f9c6e46c2eaae614fa39df5a0309840ed18bbafc866c242b8d7186a665e377 0.600000000000 1457133 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": 996717, "vin": [ { "gen": { "height": 996707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f9c6e46c2eaae614fa39df5a0309840ed18bbafc866c242b8d7186a665e377" } } ], "extra": [ 1, 18, 155, 86, 113, 76, 29, 31, 202, 223, 23, 82, 182, 130, 98, 237, 43, 137, 104, 54, 163, 45, 18, 210, 17, 206, 24, 82, 13, 250, 66, 239, 124, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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