Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd1437d2d17c5fee81ad953ba98b8b65461facd9034cd92868c4021135050b3

Tx prefix hash: 8b95bcf053f6adc9a17c8415c72bc4d84a26ee9bc4fbe1e8b09fa45a126301d2
Tx public key: 21b349ef8098fecdfa2beaa6d7a28c120fdf817ea49dc460938b1788d76a42ec
Timestamp: 1734826780 Timestamp [UCT]: 2024-12-22 00:19:40 Age [y:d:h:m:s]: 00:000:11:40:51
Block: 1180393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340 RingCT/type: yes/0
Extra: 0121b349ef8098fecdfa2beaa6d7a28c120fdf817ea49dc460938b1788d76a42ec0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa4ab9b7facf5364123242be2e61fe8e72e8f9a48c3cbaa1d7363b5c3be8e83d 0.600000000000 1666804 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": 1180403, "vin": [ { "gen": { "height": 1180393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa4ab9b7facf5364123242be2e61fe8e72e8f9a48c3cbaa1d7363b5c3be8e83d" } } ], "extra": [ 1, 33, 179, 73, 239, 128, 152, 254, 205, 250, 43, 234, 166, 215, 162, 140, 18, 15, 223, 129, 126, 164, 157, 196, 96, 147, 139, 23, 136, 215, 106, 66, 236, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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