Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e44a4044ea1e003d55c4a5a14ff219e764417910fe165a8acc623ef910d95e85

Tx prefix hash: d5864ee78bdc426bcdf58467f229f86730314f401e5bf746e9c701359ba1d5a5
Tx public key: aa3f3514e97e44086a0c7ce9ade839c8a51d052dc0bd2430aeada44c1e399c63
Timestamp: 1700366198 Timestamp [UCT]: 2023-11-19 03:56:38 Age [y:d:h:m:s]: 01:357:20:47:12
Block: 894776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514670 RingCT/type: yes/0
Extra: 01aa3f3514e97e44086a0c7ce9ade839c8a51d052dc0bd2430aeada44c1e399c6302110000000575e3f0e9000000000000000000

1 output(s) for total of 0.665634255000 dcy

stealth address amount amount idx
00: 5e8e75962dd81278b67ac8b1c4132ab00085209a32b40a0c6accdf30b571e49e 0.665634255000 1350985 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": 894786, "vin": [ { "gen": { "height": 894776 } } ], "vout": [ { "amount": 665634255, "target": { "key": "5e8e75962dd81278b67ac8b1c4132ab00085209a32b40a0c6accdf30b571e49e" } } ], "extra": [ 1, 170, 63, 53, 20, 233, 126, 68, 8, 106, 12, 124, 233, 173, 232, 57, 200, 165, 29, 5, 45, 192, 189, 36, 48, 174, 173, 164, 76, 30, 57, 156, 99, 2, 17, 0, 0, 0, 5, 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