Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75617596e677529836119f30329d9d8b8677c5945bdc69f8e53717489abd376

Tx prefix hash: 516aec4df492d63a5d569754a1c861b37e9e6e9486adbecbb550fd73ce2ebdd2
Tx public key: 8d4d77e77bbd324031287890c001f207664a91508c0a2a761bd275af6e54b47a
Timestamp: 1686277780 Timestamp [UCT]: 2023-06-09 02:29:40 Age [y:d:h:m:s]: 01:159:23:01:09
Block: 778235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375680 RingCT/type: yes/0
Extra: 018d4d77e77bbd324031287890c001f207664a91508c0a2a761bd275af6e54b47a02110000000675e3f0e9000000000000000000

1 output(s) for total of 1.619513401000 dcy

stealth address amount amount idx
00: aa8d4ee2112f6d4df5895c7a3374aa09895555f66db2ff0026899f1c5c84ddda 1.619513401000 1227856 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": 778245, "vin": [ { "gen": { "height": 778235 } } ], "vout": [ { "amount": 1619513401, "target": { "key": "aa8d4ee2112f6d4df5895c7a3374aa09895555f66db2ff0026899f1c5c84ddda" } } ], "extra": [ 1, 141, 77, 119, 231, 123, 189, 50, 64, 49, 40, 120, 144, 192, 1, 242, 7, 102, 74, 145, 80, 140, 10, 42, 118, 27, 210, 117, 175, 110, 84, 180, 122, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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