Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20ce408648d56d2623536c9c72c6e8cc50fc5f4ac5c428590062270fe6267af8

Tx prefix hash: 0515c5143f78f111bf05488db657a3bde9c0736249d62cbbce5a5b48b3d40b57
Tx public key: a3cf2a7bcdf498cbf0cb1c8f59e78a7b8eff085fbcb29738168f2a653d2773f9
Timestamp: 1713022495 Timestamp [UCT]: 2024-04-13 15:34:55 Age [y:d:h:m:s]: 01:045:12:24:42
Block: 999685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293539 RingCT/type: yes/0
Extra: 01a3cf2a7bcdf498cbf0cb1c8f59e78a7b8eff085fbcb29738168f2a653d2773f902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 320c2a24267e2d60fa746938631c5e7590dd2e30628fea513cee54fc65ab3076 0.600000000000 1460167 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": 999695, "vin": [ { "gen": { "height": 999685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "320c2a24267e2d60fa746938631c5e7590dd2e30628fea513cee54fc65ab3076" } } ], "extra": [ 1, 163, 207, 42, 123, 205, 244, 152, 203, 240, 203, 28, 143, 89, 231, 138, 123, 142, 255, 8, 95, 188, 178, 151, 56, 22, 143, 42, 101, 61, 39, 115, 249, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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