Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ef670d824777dcf9a544457047e63c80b09c19be53700e36a3cd5051bd82a1

Tx prefix hash: 50d9771c7bb354a013b1126df638321c71b6c63dd1159e1603d78f81186f4d6b
Tx public key: 92f19468e7775015454b9f6641d254dfa29e04b3b7868f7a54f3f8cae5c3e704
Timestamp: 1713439713 Timestamp [UCT]: 2024-04-18 11:28:33 Age [y:d:h:m:s]: 01:264:01:05:10
Block: 1003152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447463 RingCT/type: yes/0
Extra: 0192f19468e7775015454b9f6641d254dfa29e04b3b7868f7a54f3f8cae5c3e7040211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d106f7e28350115811f2e7801974448deba65f1b15882ffffad5ed791d35580c 0.600000000000 1463682 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": 1003162, "vin": [ { "gen": { "height": 1003152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d106f7e28350115811f2e7801974448deba65f1b15882ffffad5ed791d35580c" } } ], "extra": [ 1, 146, 241, 148, 104, 231, 119, 80, 21, 69, 75, 159, 102, 65, 210, 84, 223, 162, 158, 4, 179, 183, 134, 143, 122, 84, 243, 248, 202, 229, 195, 231, 4, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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