Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf4ee3f42a53c80bb1ff3187397f1c0745ce0c0dd24eb864da1ce2f731d3149

Tx prefix hash: c889617c2c6cdbfff795f7cab4e4a1ac4b951fe48b809a6674fb5ba7eea8977c
Tx public key: 59013ff915dbeb048798aa24d694956d2861dc4b7451f71be56ad9f271768a15
Timestamp: 1583749202 Timestamp [UCT]: 2020-03-09 10:20:02 Age [y:d:h:m:s]: 05:066:16:26:38
Block: 78964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203482 RingCT/type: yes/0
Extra: 0159013ff915dbeb048798aa24d694956d2861dc4b7451f71be56ad9f271768a1502110000000178e4872e000000000000000000

1 output(s) for total of 336.022059413000 dcy

stealth address amount amount idx
00: 15037f582088679639a91bbdb46de51471a3f52648ae13c2e0d8ed7eb9200081 336.022059413000 144676 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": 78974, "vin": [ { "gen": { "height": 78964 } } ], "vout": [ { "amount": 336022059413, "target": { "key": "15037f582088679639a91bbdb46de51471a3f52648ae13c2e0d8ed7eb9200081" } } ], "extra": [ 1, 89, 1, 63, 249, 21, 219, 235, 4, 135, 152, 170, 36, 214, 148, 149, 109, 40, 97, 220, 75, 116, 81, 247, 27, 229, 106, 217, 242, 113, 118, 138, 21, 2, 17, 0, 0, 0, 1, 120, 228, 135, 46, 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