Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f1187f69f277023ada11efd02beb44b0d41f29e6e6012bc91db836f9da65ee

Tx prefix hash: 6cd2a9f4518a36adb8633eef73dc3e4f7399e929b60bb1a9dc5cef64b62e1eed
Tx public key: fee1bc0fd695f64c2a1b97b152d7adf562654989389e9e9b2c4be48bf6417757
Timestamp: 1682346964 Timestamp [UCT]: 2023-04-24 14:36:04 Age [y:d:h:m:s]: 02:012:18:58:09
Block: 745639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531283 RingCT/type: yes/0
Extra: 01fee1bc0fd695f64c2a1b97b152d7adf562654989389e9e9b2c4be48bf641775702110000000333af99f4000000000000000000

1 output(s) for total of 2.076771298000 dcy

stealth address amount amount idx
00: 42f840ca8bf2c11f98289d39da8fff359d07fa67c60da87117f335285c9d8d4e 2.076771298000 1193108 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": 745649, "vin": [ { "gen": { "height": 745639 } } ], "vout": [ { "amount": 2076771298, "target": { "key": "42f840ca8bf2c11f98289d39da8fff359d07fa67c60da87117f335285c9d8d4e" } } ], "extra": [ 1, 254, 225, 188, 15, 214, 149, 246, 76, 42, 27, 151, 177, 82, 215, 173, 245, 98, 101, 73, 137, 56, 158, 158, 155, 44, 75, 228, 139, 246, 65, 119, 87, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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