Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 015d9b663728031893cbb84d5060bc7804715a2bfea013b1ff9abc5b62996376

Tx prefix hash: bde9af3720009048c167812d0575b420eb52e0695433976795c1eafa4547506e
Tx public key: ef1abb60deefcba1c456082e79c623a1e5e409d9ebfe421a9a613e0e0ee09fb5
Timestamp: 1717452547 Timestamp [UCT]: 2024-06-03 22:09:07 Age [y:d:h:m:s]: 00:303:05:30:13
Block: 1036439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216693 RingCT/type: yes/0
Extra: 01ef1abb60deefcba1c456082e79c623a1e5e409d9ebfe421a9a613e0e0ee09fb502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c69d054802973965adaea0c0584a15f34ce52560783d3f1cbe140718f7fd96a 0.600000000000 1504966 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": 1036449, "vin": [ { "gen": { "height": 1036439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c69d054802973965adaea0c0584a15f34ce52560783d3f1cbe140718f7fd96a" } } ], "extra": [ 1, 239, 26, 187, 96, 222, 239, 203, 161, 196, 86, 8, 46, 121, 198, 35, 161, 229, 228, 9, 217, 235, 254, 66, 26, 154, 97, 62, 14, 14, 224, 159, 181, 2, 17, 0, 0, 0, 1, 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