Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0df3b01ebf2bbd233026fd4e6ef7da3a21987985b9cc3c59cc4fa7eed5d692d

Tx prefix hash: 138c8891533bd6836989dafb52f9dda27919ffc840b7d080854982f3b213f009
Tx public key: 1754834d0bbe703bad0ca51b9bed1aa96d89874cb88b52b422185b583a13a2fb
Timestamp: 1710365146 Timestamp [UCT]: 2024-03-13 21:25:46 Age [y:d:h:m:s]: 01:023:08:45:52
Block: 977694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277674 RingCT/type: yes/0
Extra: 011754834d0bbe703bad0ca51b9bed1aa96d89874cb88b52b422185b583a13a2fb02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e91f7dbc3e9f523ab46a0f7add33232f1f9248dccca20f98b9f3a21dae04f3bf 0.600000000000 1437697 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": 977704, "vin": [ { "gen": { "height": 977694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e91f7dbc3e9f523ab46a0f7add33232f1f9248dccca20f98b9f3a21dae04f3bf" } } ], "extra": [ 1, 23, 84, 131, 77, 11, 190, 112, 59, 173, 12, 165, 27, 155, 237, 26, 169, 109, 137, 135, 76, 184, 139, 82, 180, 34, 24, 91, 88, 58, 19, 162, 251, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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