Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c95b5ea07c20fa45ecf3bcbb036194a394de1b54d079d156ce2ea4bfe44d57bd

Tx prefix hash: 01a04d2baf17e41835e1135f1ab6dcab0b6b3ca256611f86b29ba6ccd374755c
Tx public key: 390b58ad41fcd510be8a73dbcb7b97798150b562d8a18dbf21b260343d150629
Timestamp: 1677818445 Timestamp [UCT]: 2023-03-03 04:40:45 Age [y:d:h:m:s]: 02:053:06:27:26
Block: 708737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559653 RingCT/type: yes/0
Extra: 01390b58ad41fcd510be8a73dbcb7b97798150b562d8a18dbf21b260343d1506290211000000025029cbac000000000000000000

1 output(s) for total of 2.752073375000 dcy

stealth address amount amount idx
00: 3feb6c028be0e7f2d426acd8d1841d9141d954c53d81e0809355647d3e497758 2.752073375000 1152648 of 0

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": 708747, "vin": [ { "gen": { "height": 708737 } } ], "vout": [ { "amount": 2752073375, "target": { "key": "3feb6c028be0e7f2d426acd8d1841d9141d954c53d81e0809355647d3e497758" } } ], "extra": [ 1, 57, 11, 88, 173, 65, 252, 213, 16, 190, 138, 115, 219, 203, 123, 151, 121, 129, 80, 181, 98, 216, 161, 141, 191, 33, 178, 96, 52, 61, 21, 6, 41, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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