Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 368956944903b14481e7cb42b301a8c0af237008c441156526aa16142618f57f

Tx prefix hash: 753c6ff92202057b6618d5a46d2eeaa21454a4f65373b48f32adace77bc2296d
Tx public key: 05025f8dcfa796d333078dbc503c68e144d3228a991e8bcfb1ebaa8f65f28e27
Timestamp: 1733531805 Timestamp [UCT]: 2024-12-07 00:36:45 Age [y:d:h:m:s]: 00:106:15:05:00
Block: 1169634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76017 RingCT/type: yes/0
Extra: 0105025f8dcfa796d333078dbc503c68e144d3228a991e8bcfb1ebaa8f65f28e27021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9c4b2076dcdbcb2afc35e448e0505d4bcc34f972b45a131e0d65257287d2257 0.600000000000 1655355 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": 1169644, "vin": [ { "gen": { "height": 1169634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9c4b2076dcdbcb2afc35e448e0505d4bcc34f972b45a131e0d65257287d2257" } } ], "extra": [ 1, 5, 2, 95, 141, 207, 167, 150, 211, 51, 7, 141, 188, 80, 60, 104, 225, 68, 211, 34, 138, 153, 30, 139, 207, 177, 235, 170, 143, 101, 242, 142, 39, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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