Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65989f54792119fac1f488d4f2af6bebdd49ed52b8b6f696926b5f346fad7b4b

Tx prefix hash: 46f069c19f0b629381d4dc70ef95d324d4bbcee7ac1f4537790c7dd2fc1b3539
Tx public key: c917e923a3b380da90cc253416d4c95e2f56397ce320fa347f15da161281980b
Timestamp: 1713139486 Timestamp [UCT]: 2024-04-15 00:04:46 Age [y:d:h:m:s]: 00:337:09:57:20
Block: 1000654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241254 RingCT/type: yes/0
Extra: 01c917e923a3b380da90cc253416d4c95e2f56397ce320fa347f15da161281980b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd5a0bfae63c3e3ecd66f46a43d18668f5afaf9365e8d00b4ebf3f7dd5e443d 0.600000000000 1461152 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": 1000664, "vin": [ { "gen": { "height": 1000654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd5a0bfae63c3e3ecd66f46a43d18668f5afaf9365e8d00b4ebf3f7dd5e443d" } } ], "extra": [ 1, 201, 23, 233, 35, 163, 179, 128, 218, 144, 204, 37, 52, 22, 212, 201, 94, 47, 86, 57, 124, 227, 32, 250, 52, 127, 21, 218, 22, 18, 129, 152, 11, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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