Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed9db0cabd93ef6bc1a1273e6939915033aa72f947f2ff23e222068991ad494

Tx prefix hash: 3fb7152ec5ab6c68168234f168a6d1d2b2285c26f83066e7c86d2ffd8da1f0f8
Tx public key: 819c01e03b1c91adba50f91019176561eab3c9b45ff2311310a64f1702cf0d0b
Timestamp: 1723955753 Timestamp [UCT]: 2024-08-18 04:35:53 Age [y:d:h:m:s]: 00:235:05:12:02
Block: 1090358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167976 RingCT/type: yes/0
Extra: 01819c01e03b1c91adba50f91019176561eab3c9b45ff2311310a64f1702cf0d0b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b71555bd532ac6e1bd04b633e2c07abc0455bbb96be1766c0d1b790617c42c1c 0.600000000000 1564981 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": 1090368, "vin": [ { "gen": { "height": 1090358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b71555bd532ac6e1bd04b633e2c07abc0455bbb96be1766c0d1b790617c42c1c" } } ], "extra": [ 1, 129, 156, 1, 224, 59, 28, 145, 173, 186, 80, 249, 16, 25, 23, 101, 97, 234, 179, 201, 180, 95, 242, 49, 19, 16, 166, 79, 23, 2, 207, 13, 11, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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