Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 066e3bd86cfcafd4ec878d023f4bdcf064d671dd38503c277959e5dac147c181

Tx prefix hash: c540b837e04678005eed07c85d0bab0cff136eee22863f77f6e15cfb85269a84
Tx public key: fbfdc47f61f9ebeb5b431f6fa22cdbf507833850e9da10bc32dc6046bf5f4bfe
Timestamp: 1701875494 Timestamp [UCT]: 2023-12-06 15:11:34 Age [y:d:h:m:s]: 01:133:23:35:56
Block: 907289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356925 RingCT/type: yes/0
Extra: 01fbfdc47f61f9ebeb5b431f6fa22cdbf507833850e9da10bc32dc6046bf5f4bfe021100000004faf35c9c000000000000000000

1 output(s) for total of 0.605027176000 dcy

stealth address amount amount idx
00: 57089ccf7e76d03431c7d8a0578bc1326c38cb24c028ed3005963edf5c49b7ea 0.605027176000 1364272 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": 907299, "vin": [ { "gen": { "height": 907289 } } ], "vout": [ { "amount": 605027176, "target": { "key": "57089ccf7e76d03431c7d8a0578bc1326c38cb24c028ed3005963edf5c49b7ea" } } ], "extra": [ 1, 251, 253, 196, 127, 97, 249, 235, 235, 91, 67, 31, 111, 162, 44, 219, 245, 7, 131, 56, 80, 233, 218, 16, 188, 50, 220, 96, 70, 191, 95, 75, 254, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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