Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c92d393d6a0e58e9d6b1bd7ff425f6e4f447aebdc19c64e8e9924fcab16badf

Tx prefix hash: 35cb3e85575c981cc59962241f746134deb935c38ca3f2ca36bf082b13de2764
Tx public key: 90bec0c4e956e3d576d25895972a33f472fe7fd7e38762dd4910c43eaf3470a5
Timestamp: 1705167198 Timestamp [UCT]: 2024-01-13 17:33:18 Age [y:d:h:m:s]: 01:105:06:11:34
Block: 934569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336354 RingCT/type: yes/0
Extra: 0190bec0c4e956e3d576d25895972a33f472fe7fd7e38762dd4910c43eaf3470a502110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5949e15daec8c6c4139a41381bc598178dafcaa87b790b1cc244a4b854587ec1 0.600000000000 1392583 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": 934579, "vin": [ { "gen": { "height": 934569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5949e15daec8c6c4139a41381bc598178dafcaa87b790b1cc244a4b854587ec1" } } ], "extra": [ 1, 144, 190, 192, 196, 233, 86, 227, 213, 118, 210, 88, 149, 151, 42, 51, 244, 114, 254, 127, 215, 227, 135, 98, 221, 73, 16, 196, 62, 175, 52, 112, 165, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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