Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ede4a1eb17e6a2183242060631e053cb3b34166e870395364dff8736945bc36c

Tx prefix hash: 2a00971574cdd687ed508ac74d3ac7d12b5ef769c021feaa4a848ebfb90321ea
Tx public key: c7be8c448051456705c22964598e4206a6a9738a8ae820a51849a9a4194b35f8
Timestamp: 1711628375 Timestamp [UCT]: 2024-03-28 12:19:35 Age [y:d:h:m:s]: 01:079:21:46:21
Block: 988161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318002 RingCT/type: yes/0
Extra: 01c7be8c448051456705c22964598e4206a6a9738a8ae820a51849a9a4194b35f802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53ca33946bf089e0b6d323df4ae748e52beb63b8d5a4ece2da2e30ff8f821a37 0.600000000000 1448428 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": 988171, "vin": [ { "gen": { "height": 988161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53ca33946bf089e0b6d323df4ae748e52beb63b8d5a4ece2da2e30ff8f821a37" } } ], "extra": [ 1, 199, 190, 140, 68, 128, 81, 69, 103, 5, 194, 41, 100, 89, 142, 66, 6, 166, 169, 115, 138, 138, 232, 32, 165, 24, 73, 169, 164, 25, 75, 53, 248, 2, 17, 0, 0, 0, 5, 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