Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31c0c071ef201b97b3ce8c05e4a6092c4932a95c793eaf675a632e33eab34016

Tx prefix hash: e8cbe718ab56afea38ba0fdbdd9801b1d203892f4d65ead4b065784109862db8
Tx public key: 0f13e94d1f80e5e2e8444464548ba86c91f3c8fa4f50b71f1ecf6d37b4dac0d8
Timestamp: 1586246401 Timestamp [UCT]: 2020-04-07 08:00:01 Age [y:d:h:m:s]: 05:033:23:26:07
Block: 91679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1188047 RingCT/type: yes/0
Extra: 010f13e94d1f80e5e2e8444464548ba86c91f3c8fa4f50b71f1ecf6d37b4dac0d8021100000002209b4bc8000000000000000000

1 output(s) for total of 304.951088636000 dcy

stealth address amount amount idx
00: 4da99e8ac323a52813e8442857e8c39d26272e9cd92e3ae0a59df63f1838785b 304.951088636000 163909 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": 91689, "vin": [ { "gen": { "height": 91679 } } ], "vout": [ { "amount": 304951088636, "target": { "key": "4da99e8ac323a52813e8442857e8c39d26272e9cd92e3ae0a59df63f1838785b" } } ], "extra": [ 1, 15, 19, 233, 77, 31, 128, 229, 226, 232, 68, 68, 100, 84, 139, 168, 108, 145, 243, 200, 250, 79, 80, 183, 31, 30, 207, 109, 55, 180, 218, 192, 216, 2, 17, 0, 0, 0, 2, 32, 155, 75, 200, 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