Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a40c4327f1a3bac2259cf8e736c3d83d190be51b935d1bd21017d8ec2954a32

Tx prefix hash: 8903861dd51b79c46341e5447597bb94ada2d42ce2a34c99ad96c6d3b2bbd2fe
Tx public key: dbca69523dfb91dca0d6af7488b46938a022ae6bf6846f21b7f650ca494a5dd6
Timestamp: 1729406356 Timestamp [UCT]: 2024-10-20 06:39:16 Age [y:d:h:m:s]: 00:094:16:27:21
Block: 1135530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67636 RingCT/type: yes/0
Extra: 01dbca69523dfb91dca0d6af7488b46938a022ae6bf6846f21b7f650ca494a5dd6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6078e3995a3f1bc7c89b9f13f0e5155a95b7e9e541a930d94fd7ee44579fa66e 0.600000000000 1618867 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": 1135540, "vin": [ { "gen": { "height": 1135530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6078e3995a3f1bc7c89b9f13f0e5155a95b7e9e541a930d94fd7ee44579fa66e" } } ], "extra": [ 1, 219, 202, 105, 82, 61, 251, 145, 220, 160, 214, 175, 116, 136, 180, 105, 56, 160, 34, 174, 107, 246, 132, 111, 33, 183, 246, 80, 202, 73, 74, 93, 214, 2, 17, 0, 0, 0, 3, 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