Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b465addfb6d1b9d34d783f26db64fa945caa018ea2f6b6d4d29d943ba0fd4e

Tx prefix hash: aaba68d55cd08ce2e09723a5c102fdcabaf49bc0993f8578a8df609603305015
Tx public key: 02bc1621d22156b0a2be321e293d9f6092408476d78e00c49d6356e56ed2ad33
Timestamp: 1577564089 Timestamp [UCT]: 2019-12-28 20:14:49 Age [y:d:h:m:s]: 05:009:06:01:34
Block: 33801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156641 RingCT/type: yes/0
Extra: 0102bc1621d22156b0a2be321e293d9f6092408476d78e00c49d6356e56ed2ad3302110000000578873133000000000000000000

1 output(s) for total of 474.262855790000 dcy

stealth address amount amount idx
00: 4bae40963a32cee2c6d89207abee9d6bc83fda5ece099fea021998608b6cf3cb 474.262855790000 56718 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": 33811, "vin": [ { "gen": { "height": 33801 } } ], "vout": [ { "amount": 474262855790, "target": { "key": "4bae40963a32cee2c6d89207abee9d6bc83fda5ece099fea021998608b6cf3cb" } } ], "extra": [ 1, 2, 188, 22, 33, 210, 33, 86, 176, 162, 190, 50, 30, 41, 61, 159, 96, 146, 64, 132, 118, 215, 142, 0, 196, 157, 99, 86, 229, 110, 210, 173, 51, 2, 17, 0, 0, 0, 5, 120, 135, 49, 51, 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