Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44b7de37dfc7f822fa0c6c9a83dafcab9b1d1d4acfc0ad942772496efbac7a2

Tx prefix hash: 06c658d8bde632cf6675de5d42aa957fb87cf58ddeb95769e01f8cffbccd6946
Tx public key: 29f6ce1ef9919559488a4edee9c83a6baf8fed642a335610e8cf8d3fc73f85b3
Timestamp: 1720142036 Timestamp [UCT]: 2024-07-05 01:13:56 Age [y:d:h:m:s]: 01:126:14:24:11
Block: 1058723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349015 RingCT/type: yes/0
Extra: 0129f6ce1ef9919559488a4edee9c83a6baf8fed642a335610e8cf8d3fc73f85b30211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad916fecffaa35a31a6d5494f984ba38b85f2b412eaa89d6eda5557bc15c459c 0.600000000000 1529180 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": 1058733, "vin": [ { "gen": { "height": 1058723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad916fecffaa35a31a6d5494f984ba38b85f2b412eaa89d6eda5557bc15c459c" } } ], "extra": [ 1, 41, 246, 206, 30, 249, 145, 149, 89, 72, 138, 78, 222, 233, 200, 58, 107, 175, 143, 237, 100, 42, 51, 86, 16, 232, 207, 141, 63, 199, 63, 133, 179, 2, 17, 0, 0, 0, 4, 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