Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c03a66d2e01604bb94338c2ffac65a87f056238abb89ecb33efdfcbb2205680a

Tx prefix hash: 4a4bbd3165a83aacd0c41493a8e60a87180e994643bdf2225b3b406f76c809bc
Tx public key: f29c383d0cc8fde4000b6d0f6e4d722772cd2212e0b510cf97f87aa6c2327ffd
Timestamp: 1703589922 Timestamp [UCT]: 2023-12-26 11:25:22 Age [y:d:h:m:s]: 01:316:22:39:01
Block: 921509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485353 RingCT/type: yes/0
Extra: 01f29c383d0cc8fde4000b6d0f6e4d722772cd2212e0b510cf97f87aa6c2327ffd02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 759cc94e7ac7358ca9ec019ece509544aa7305ac9efb00ad1dc9e8e0f5c0927f 0.600000000000 1379197 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": 921519, "vin": [ { "gen": { "height": 921509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "759cc94e7ac7358ca9ec019ece509544aa7305ac9efb00ad1dc9e8e0f5c0927f" } } ], "extra": [ 1, 242, 156, 56, 61, 12, 200, 253, 228, 0, 11, 109, 15, 110, 77, 114, 39, 114, 205, 34, 18, 224, 181, 16, 207, 151, 248, 122, 166, 194, 50, 127, 253, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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