Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aafd8341f21535d5a7311a1de6402b70178c8bb17b6eb6caf30cece951f78926

Tx prefix hash: 332ffbe771757de664d1da679afa6f2c599ea0b48f1e88332814037cb4a8cf47
Tx public key: 363f48bf05b701751894025e2fdeed39a28a5fff2e9eec5bf5b4f72e5873ae7b
Timestamp: 1737050686 Timestamp [UCT]: 2025-01-16 18:04:46 Age [y:d:h:m:s]: 00:153:03:21:21
Block: 1198767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109141 RingCT/type: yes/0
Extra: 01363f48bf05b701751894025e2fdeed39a28a5fff2e9eec5bf5b4f72e5873ae7b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e83ae4dd9bbd2d86b7b7659a3a3aae66a01b80c267028a10c5a10038db9979f3 0.600000000000 1685394 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": 1198777, "vin": [ { "gen": { "height": 1198767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e83ae4dd9bbd2d86b7b7659a3a3aae66a01b80c267028a10c5a10038db9979f3" } } ], "extra": [ 1, 54, 63, 72, 191, 5, 183, 1, 117, 24, 148, 2, 94, 47, 222, 237, 57, 162, 138, 95, 255, 46, 158, 236, 91, 245, 180, 247, 46, 88, 115, 174, 123, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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