Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 655a9a4f44aba967592ae002ec2d69928f7d81e4ec0a77a1fdbe90d219c639bb

Tx prefix hash: b4391fdf9bc1eb08dd43bb2ea54cf12f1c760b8420cc100e0bcfe9a1dd9b7d09
Tx public key: 1861fdd82c8cf63f89fff291e997ab2d489fdbd9660b088736081c4bd305ec8c
Timestamp: 1721418634 Timestamp [UCT]: 2024-07-19 19:50:34 Age [y:d:h:m:s]: 00:096:00:48:01
Block: 1069342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68733 RingCT/type: yes/0
Extra: 011861fdd82c8cf63f89fff291e997ab2d489fdbd9660b088736081c4bd305ec8c021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a0a7c00b928aa67d6358ab10ce33ed059c6496eada49b8b308d9a16bacf293d 0.600000000000 1540727 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": 1069352, "vin": [ { "gen": { "height": 1069342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a0a7c00b928aa67d6358ab10ce33ed059c6496eada49b8b308d9a16bacf293d" } } ], "extra": [ 1, 24, 97, 253, 216, 44, 140, 246, 63, 137, 255, 242, 145, 233, 151, 171, 45, 72, 159, 219, 217, 102, 11, 8, 135, 54, 8, 28, 75, 211, 5, 236, 140, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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