Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbb7ae3e6435d85c41c633c6d112edae379a9423fc0a12997167809f3b16e997

Tx prefix hash: 8a7040f025dc597c75dfa55461d05c8a6b5f060851c32dfb383383d9026b6b63
Tx public key: 1e03152be355645e0c2a46c2a104b6f01f956fc256f5dda7591a5413db25e25d
Timestamp: 1736914997 Timestamp [UCT]: 2025-01-15 04:23:17 Age [y:d:h:m:s]: 00:154:19:27:56
Block: 1197634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110342 RingCT/type: yes/0
Extra: 011e03152be355645e0c2a46c2a104b6f01f956fc256f5dda7591a5413db25e25d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d3a6af66fc03eb346e66eca2a932be9d046dc5ec6bf8dff08b31f2ddf3c23e4 0.600000000000 1684247 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": 1197644, "vin": [ { "gen": { "height": 1197634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d3a6af66fc03eb346e66eca2a932be9d046dc5ec6bf8dff08b31f2ddf3c23e4" } } ], "extra": [ 1, 30, 3, 21, 43, 227, 85, 100, 94, 12, 42, 70, 194, 161, 4, 182, 240, 31, 149, 111, 194, 86, 245, 221, 167, 89, 26, 84, 19, 219, 37, 226, 93, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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