Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e15cb3be371104a0cb6897d429cd9eac1fe4aee6a091d572a4290f86401c5f8d

Tx prefix hash: 5f2b5f05fdac22541f014b7f71b75ec5bbe99638c88fae5195d26aa0a099fb65
Tx public key: c3e0a7e95f7be4d0a3dc90364892a6b4ddcd162d5af73bde0b60708819697122
Timestamp: 1727665803 Timestamp [UCT]: 2024-09-30 03:10:03 Age [y:d:h:m:s]: 00:103:16:31:19
Block: 1121111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74118 RingCT/type: yes/0
Extra: 01c3e0a7e95f7be4d0a3dc90364892a6b4ddcd162d5af73bde0b60708819697122021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 225b1cea4d34e4d3e4c42931949c54e033b4c93e99e28c53f7d04c70bcfc967b 0.600000000000 1603266 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": 1121121, "vin": [ { "gen": { "height": 1121111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "225b1cea4d34e4d3e4c42931949c54e033b4c93e99e28c53f7d04c70bcfc967b" } } ], "extra": [ 1, 195, 224, 167, 233, 95, 123, 228, 208, 163, 220, 144, 54, 72, 146, 166, 180, 221, 205, 22, 45, 90, 247, 59, 222, 11, 96, 112, 136, 25, 105, 113, 34, 2, 17, 0, 0, 0, 2, 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