Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0742d118122e72c916b92b5caceeb0b185b0ef2128010d9b874b96653ab79045

Tx prefix hash: 40019bf50e586505f7bbf4fd0e36e8e223e017cb998890e3c30814302fe572b1
Tx public key: a7eb3d6e07155b184738b6c1d1116ae7c0461c673b6a0247e94c4070596251d1
Timestamp: 1729885753 Timestamp [UCT]: 2024-10-25 19:49:13 Age [y:d:h:m:s]: 00:165:11:29:24
Block: 1139476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118073 RingCT/type: yes/0
Extra: 01a7eb3d6e07155b184738b6c1d1116ae7c0461c673b6a0247e94c4070596251d1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92f85594c210c4bb8d5ab2e95e93ed8b5d9b20b7c126efddbe5d116572c0414f 0.600000000000 1623263 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": 1139486, "vin": [ { "gen": { "height": 1139476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92f85594c210c4bb8d5ab2e95e93ed8b5d9b20b7c126efddbe5d116572c0414f" } } ], "extra": [ 1, 167, 235, 61, 110, 7, 21, 91, 24, 71, 56, 182, 193, 209, 17, 106, 231, 192, 70, 28, 103, 59, 106, 2, 71, 233, 76, 64, 112, 89, 98, 81, 209, 2, 17, 0, 0, 0, 1, 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