Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794d1638db89ba34b5f1e25338a952bc40820c112474aeab16ed1fe3ffa73e30

Tx prefix hash: 6c61e235cba61034c4754640b23bd8dca331acfec4aec5dafa8f099150a9acd4
Tx public key: f940e0d53120dde0a251f0a3cfeb3f272125138b45ad819f8f5abc6abcdfaaa3
Timestamp: 1711884524 Timestamp [UCT]: 2024-03-31 11:28:44 Age [y:d:h:m:s]: 00:352:23:05:52
Block: 990297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252347 RingCT/type: yes/0
Extra: 01f940e0d53120dde0a251f0a3cfeb3f272125138b45ad819f8f5abc6abcdfaaa30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c96e8042e496281f5af42cb1381224b33e05b9103105ccd0a7a035bd68f292f5 0.600000000000 1450619 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": 990307, "vin": [ { "gen": { "height": 990297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c96e8042e496281f5af42cb1381224b33e05b9103105ccd0a7a035bd68f292f5" } } ], "extra": [ 1, 249, 64, 224, 213, 49, 32, 221, 224, 162, 81, 240, 163, 207, 235, 63, 39, 33, 37, 19, 139, 69, 173, 129, 159, 143, 90, 188, 106, 188, 223, 170, 163, 2, 17, 0, 0, 0, 1, 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