Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46f1e470977a6fc2c681dc9d7ce2139ed9e73fd4c31eb3b46d788b1ae8dd46a

Tx prefix hash: 27195a51ee74f8e2c8a7201bdd74476f355a0512d497ff82b8f5e7caaae49d4f
Tx public key: 8889f8522b5ae7c619f8d965c88f1277f50d26e2227bfa8418c6174ceb28f35e
Timestamp: 1737496305 Timestamp [UCT]: 2025-01-21 21:51:45 Age [y:d:h:m:s]: 00:146:19:43:29
Block: 1202406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104698 RingCT/type: yes/0
Extra: 018889f8522b5ae7c619f8d965c88f1277f50d26e2227bfa8418c6174ceb28f35e021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2bdcb9b8a411d4add57a35e40cc36bae4f6607ae9d3adce3ea4bb241722db83 0.600000000000 1689069 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": 1202416, "vin": [ { "gen": { "height": 1202406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2bdcb9b8a411d4add57a35e40cc36bae4f6607ae9d3adce3ea4bb241722db83" } } ], "extra": [ 1, 136, 137, 248, 82, 43, 90, 231, 198, 25, 248, 217, 101, 200, 143, 18, 119, 245, 13, 38, 226, 34, 123, 250, 132, 24, 198, 23, 76, 235, 40, 243, 94, 2, 17, 0, 0, 0, 7, 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