Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 136c9284799e49c10878e2ab31dc1c03b61d697a1968008d79863726864d592a

Tx prefix hash: fb1efda1b59cf48f70dc9ec0d1779085c83357bf5d8fa877e8732433a0e14151
Tx public key: 2de0277ecb917d715dded6e1ce7b6d9e2e578e17a0630c867ea5fd89d0218652
Timestamp: 1631760509 Timestamp [UCT]: 2021-09-16 02:48:29 Age [y:d:h:m:s]: 04:056:05:34:35
Block: 334673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074287 RingCT/type: yes/0
Extra: 012de0277ecb917d715dded6e1ce7b6d9e2e578e17a0630c867ea5fd89d021865202110000001d37cb3088000000000000000000

1 output(s) for total of 47.762809106000 dcy

stealth address amount amount idx
00: bcb5a924176c2f0c72cd3183248c3b8ff1ee288fa2f45a3a34b0f12238ecffb7 47.762809106000 690204 of 0

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": 334683, "vin": [ { "gen": { "height": 334673 } } ], "vout": [ { "amount": 47762809106, "target": { "key": "bcb5a924176c2f0c72cd3183248c3b8ff1ee288fa2f45a3a34b0f12238ecffb7" } } ], "extra": [ 1, 45, 224, 39, 126, 203, 145, 125, 113, 93, 222, 214, 225, 206, 123, 109, 158, 46, 87, 142, 23, 160, 99, 12, 134, 126, 165, 253, 137, 208, 33, 134, 82, 2, 17, 0, 0, 0, 29, 55, 203, 48, 136, 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