Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 319c44f57a123f4e44c84684a4205c2a83c946d174bafd4316d0edeeefbd000d

Tx prefix hash: a0e84495254b80f2e35ac3616cff339ccf014c64adc5af5d95ed5d02053aaf47
Tx public key: 1fc2ea934c3791632a3905d2e1f40d40dc37281d122ef6e7cf6f62268548a4ab
Timestamp: 1705707308 Timestamp [UCT]: 2024-01-19 23:35:08 Age [y:d:h:m:s]: 01:116:12:13:23
Block: 939027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344406 RingCT/type: yes/0
Extra: 011fc2ea934c3791632a3905d2e1f40d40dc37281d122ef6e7cf6f62268548a4ab0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75bb6845ad44b242af184bd2f1874d1150cbae4ccfffd2c83722a27cd8cadc5f 0.600000000000 1397111 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": 939037, "vin": [ { "gen": { "height": 939027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75bb6845ad44b242af184bd2f1874d1150cbae4ccfffd2c83722a27cd8cadc5f" } } ], "extra": [ 1, 31, 194, 234, 147, 76, 55, 145, 99, 42, 57, 5, 210, 225, 244, 13, 64, 220, 55, 40, 29, 18, 46, 246, 231, 207, 111, 98, 38, 133, 72, 164, 171, 2, 17, 0, 0, 0, 4, 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