Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b363792a7526a50c2d0c60b7a5732138199a18759085bad105923398a3964dc3

Tx prefix hash: 7248f79b5d960c5f6c6694f8e5622fd284d4cc7cdb65fabf527d3b0583099a5f
Tx public key: 270b82f402e5b6d45c0431b29f2061159080af1aec9b1da92acff9108450a764
Timestamp: 1629981502 Timestamp [UCT]: 2021-08-26 12:38:22 Age [y:d:h:m:s]: 04:043:22:54:48
Block: 321160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1064252 RingCT/type: yes/0
Extra: 01270b82f402e5b6d45c0431b29f2061159080af1aec9b1da92acff9108450a7640211000000019de819df000000000000000000

1 output(s) for total of 52.949767762000 dcy

stealth address amount amount idx
00: e1b2a2c7285e53c0bb33a726f98e5b415593073c1e3549db7c4571d43b119d29 52.949767762000 666805 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": 321170, "vin": [ { "gen": { "height": 321160 } } ], "vout": [ { "amount": 52949767762, "target": { "key": "e1b2a2c7285e53c0bb33a726f98e5b415593073c1e3549db7c4571d43b119d29" } } ], "extra": [ 1, 39, 11, 130, 244, 2, 229, 182, 212, 92, 4, 49, 178, 159, 32, 97, 21, 144, 128, 175, 26, 236, 155, 29, 169, 42, 207, 249, 16, 132, 80, 167, 100, 2, 17, 0, 0, 0, 1, 157, 232, 25, 223, 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