Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d911ae0ca9276910b0cf6cbb590d7c13fbd8b146588bd43e91adcbf4ef7726d0

Tx prefix hash: a2e116868e02e9b70dcd982aa3c459ad117325dff4bdf0aab446d29b05f289e4
Tx public key: e366d58a8e2fdfe92b5506feb22467b721918d5c3e38fbc047afda33329f03dc
Timestamp: 1728093660 Timestamp [UCT]: 2024-10-05 02:01:00 Age [y:d:h:m:s]: 00:050:03:27:36
Block: 1124656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35819 RingCT/type: yes/0
Extra: 01e366d58a8e2fdfe92b5506feb22467b721918d5c3e38fbc047afda33329f03dc021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa13661ec8c6d6e5b88374a42f66d1cf82d4e6d42397fa5a5c5b27b13000dd38 0.600000000000 1607315 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": 1124666, "vin": [ { "gen": { "height": 1124656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa13661ec8c6d6e5b88374a42f66d1cf82d4e6d42397fa5a5c5b27b13000dd38" } } ], "extra": [ 1, 227, 102, 213, 138, 142, 47, 223, 233, 43, 85, 6, 254, 178, 36, 103, 183, 33, 145, 141, 92, 62, 56, 251, 192, 71, 175, 218, 51, 50, 159, 3, 220, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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