Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a5ee449b7228da72b4dab87811489586f6a9281f7ba7a315c29458fbd388382

Tx prefix hash: 9f753e5152939f8679096f3f1506c917216c60ed7682cd9e0fcb40460dfbc79c
Tx public key: 9e9d378854e0e40a2a3f7d3f640bc42440955a49e93e9be2d953210e22b4aa40
Timestamp: 1710039789 Timestamp [UCT]: 2024-03-10 03:03:09 Age [y:d:h:m:s]: 00:243:01:40:07
Block: 974991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174016 RingCT/type: yes/0
Extra: 019e9d378854e0e40a2a3f7d3f640bc42440955a49e93e9be2d953210e22b4aa400211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3235132020d4ff8fba6d045f89c8103dd7ef5242a343ea43011c1cea48b9b9ec 0.600000000000 1434960 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": 975001, "vin": [ { "gen": { "height": 974991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3235132020d4ff8fba6d045f89c8103dd7ef5242a343ea43011c1cea48b9b9ec" } } ], "extra": [ 1, 158, 157, 55, 136, 84, 224, 228, 10, 42, 63, 125, 63, 100, 11, 196, 36, 64, 149, 90, 73, 233, 62, 155, 226, 217, 83, 33, 14, 34, 180, 170, 64, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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