Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2727d9fb5ce37931d938c99ee18056a38c2bbb0e68ab027de4b1576d45f71171

Tx prefix hash: 297b930654dde41c5fe7b2f3c3abe73e88a1866c6390e443366b8baa18d2cf8b
Tx public key: 842c8f933ca6e8813ca27b8fa1b2d3ed6ec453b57872b3bd19184f8f500de17c
Timestamp: 1712588196 Timestamp [UCT]: 2024-04-08 14:56:36 Age [y:d:h:m:s]: 01:008:02:06:52
Block: 996081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266752 RingCT/type: yes/0
Extra: 01842c8f933ca6e8813ca27b8fa1b2d3ed6ec453b57872b3bd19184f8f500de17c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 550d3ac166268cd40574f64337c3cd347541bea5b03efdea381a5fdd4dc668c1 0.600000000000 1456497 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": 996091, "vin": [ { "gen": { "height": 996081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "550d3ac166268cd40574f64337c3cd347541bea5b03efdea381a5fdd4dc668c1" } } ], "extra": [ 1, 132, 44, 143, 147, 60, 166, 232, 129, 60, 162, 123, 143, 161, 178, 211, 237, 110, 196, 83, 181, 120, 114, 179, 189, 25, 24, 79, 143, 80, 13, 225, 124, 2, 17, 0, 0, 0, 1, 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