Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbe69da79c1c52af6bceb1241126e9eb871fa099418f93b499c799fe7fa392fb

Tx prefix hash: 6417d7f832674fb70075d8691a4f4703e556b85d142f9e8d9f1b86c4f0a8eaaf
Tx public key: ed077bdd990923e75f5c22f0eb0061ead917b541ce09d80bfed4946e9564b4bb
Timestamp: 1720624372 Timestamp [UCT]: 2024-07-10 15:12:52 Age [y:d:h:m:s]: 00:317:06:20:05
Block: 1062734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226723 RingCT/type: yes/0
Extra: 01ed077bdd990923e75f5c22f0eb0061ead917b541ce09d80bfed4946e9564b4bb02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaf13d5adb344c7f642eb078f5059ba5af33bdf2ff68ab3ab130d8ef39f704a2 0.600000000000 1533241 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": 1062744, "vin": [ { "gen": { "height": 1062734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaf13d5adb344c7f642eb078f5059ba5af33bdf2ff68ab3ab130d8ef39f704a2" } } ], "extra": [ 1, 237, 7, 123, 221, 153, 9, 35, 231, 95, 92, 34, 240, 235, 0, 97, 234, 217, 23, 181, 65, 206, 9, 216, 11, 254, 212, 148, 110, 149, 100, 180, 187, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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