Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a4775010ff7a8a853f6e193d902860f191604c4e9d1ab4960072a5572be5a77

Tx prefix hash: a57ed509030aa864de6e1d27d3364db05adfd6518ed0d8c512aafcd3e119e1fe
Tx public key: be14c939ccb040e9399cee78a37280b38d6881b416b326410f581f0f038c368b
Timestamp: 1706052917 Timestamp [UCT]: 2024-01-23 23:35:17 Age [y:d:h:m:s]: 01:085:02:47:05
Block: 941899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321933 RingCT/type: yes/0
Extra: 01be14c939ccb040e9399cee78a37280b38d6881b416b326410f581f0f038c368b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1909d532d1707e4f9a13cebfbb014bd003ffd73a35587e3f370510ca42b4ad5c 0.600000000000 1400057 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": 941909, "vin": [ { "gen": { "height": 941899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1909d532d1707e4f9a13cebfbb014bd003ffd73a35587e3f370510ca42b4ad5c" } } ], "extra": [ 1, 190, 20, 201, 57, 204, 176, 64, 233, 57, 156, 238, 120, 163, 114, 128, 179, 141, 104, 129, 180, 22, 179, 38, 65, 15, 88, 31, 15, 3, 140, 54, 139, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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