Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff6096ea889176e3b4337bdb7ecebd4fdce1e8080d21038a2b605c64897bb6cb

Tx prefix hash: c059ea7d14772a4dce2877fcb506d99431a69eba730f748f0f68c4653f8703f5
Tx public key: 21c67fb15916dd56f2d1163322550877572a81fe8ca44ecf0dfb3a86c86ffcf1
Timestamp: 1702394326 Timestamp [UCT]: 2023-12-12 15:18:46 Age [y:d:h:m:s]: 01:186:03:25:29
Block: 911612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394102 RingCT/type: yes/0
Extra: 0121c67fb15916dd56f2d1163322550877572a81fe8ca44ecf0dfb3a86c86ffcf1021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bc3380b60e6ac102da2f8a6f98d0e504bfd9b3acd64de308c13f7008a9a319f 0.600000000000 1368826 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": 911622, "vin": [ { "gen": { "height": 911612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bc3380b60e6ac102da2f8a6f98d0e504bfd9b3acd64de308c13f7008a9a319f" } } ], "extra": [ 1, 33, 198, 127, 177, 89, 22, 221, 86, 242, 209, 22, 51, 34, 85, 8, 119, 87, 42, 129, 254, 140, 164, 78, 207, 13, 251, 58, 134, 200, 111, 252, 241, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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