Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa1df73b54e3cf90efeb2eae4067e7426ac73d7ace779fb6938b161a0998b56f

Tx prefix hash: ed3641a6e5df60eef6482b2baec06c929a8276ffcc199758606e3598dd775e20
Tx public key: de4a3ac65ff4821e5646e94bb85eff6b1d964f64e192d1a713c1440d46b7bc9e
Timestamp: 1722930798 Timestamp [UCT]: 2024-08-06 07:53:18 Age [y:d:h:m:s]: 01:095:11:46:02
Block: 1081844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326739 RingCT/type: yes/0
Extra: 01de4a3ac65ff4821e5646e94bb85eff6b1d964f64e192d1a713c1440d46b7bc9e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e63c54a151c54ac316bfd0657ea8a4564fc8c06f950b0b213daab49ae3128808 0.600000000000 1555667 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": 1081854, "vin": [ { "gen": { "height": 1081844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e63c54a151c54ac316bfd0657ea8a4564fc8c06f950b0b213daab49ae3128808" } } ], "extra": [ 1, 222, 74, 58, 198, 95, 244, 130, 30, 86, 70, 233, 75, 184, 94, 255, 107, 29, 150, 79, 100, 225, 146, 209, 167, 19, 193, 68, 13, 70, 183, 188, 158, 2, 17, 0, 0, 0, 1, 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