Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34e42512ba4e3dd99d2dcb114053dadbf048b71f7da9e9f51434b356f22a797

Tx prefix hash: bd4206d958afb0f3dece04b8a3482a598da68efd085a53d823440f1590cc2e88
Tx public key: a7b3497a36ffcca3d5cf8422c7b132887ea6549274a03c53211513f32f3b157a
Timestamp: 1705613355 Timestamp [UCT]: 2024-01-18 21:29:15 Age [y:d:h:m:s]: 01:084:01:28:25
Block: 938265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321183 RingCT/type: yes/0
Extra: 01a7b3497a36ffcca3d5cf8422c7b132887ea6549274a03c53211513f32f3b157a02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbfa479cbe7c7b9967965b1104af33f71138eaf4105237c879505bb9d313164a 0.600000000000 1396335 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": 938275, "vin": [ { "gen": { "height": 938265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbfa479cbe7c7b9967965b1104af33f71138eaf4105237c879505bb9d313164a" } } ], "extra": [ 1, 167, 179, 73, 122, 54, 255, 204, 163, 213, 207, 132, 34, 199, 177, 50, 136, 126, 166, 84, 146, 116, 160, 60, 83, 33, 21, 19, 243, 47, 59, 21, 122, 2, 17, 0, 0, 0, 11, 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