Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a05d4572ab2cac432a157fcf636975e34ce0c35f53007d0fe28116708a3af7fa

Tx prefix hash: f272c38567c32bbd7d6fea6b4a76e2e24be8dd24af5fa03da5e5334aa7e55b57
Tx public key: b544a15b60c9bd2d2c52e5586510a650e68c4bb1e421f8196727c391422125c8
Timestamp: 1577879466 Timestamp [UCT]: 2020-01-01 11:51:06 Age [y:d:h:m:s]: 04:276:06:36:59
Block: 36314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086698 RingCT/type: yes/0
Extra: 01b544a15b60c9bd2d2c52e5586510a650e68c4bb1e421f8196727c391422125c80211000000334943cd9f000000000000000000

1 output(s) for total of 465.240481337000 dcy

stealth address amount amount idx
00: d65704e002c3cb79276cdad202c68f50e1875bbf5b5216992f999fe420c1f244 465.240481337000 61485 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": 36324, "vin": [ { "gen": { "height": 36314 } } ], "vout": [ { "amount": 465240481337, "target": { "key": "d65704e002c3cb79276cdad202c68f50e1875bbf5b5216992f999fe420c1f244" } } ], "extra": [ 1, 181, 68, 161, 91, 96, 201, 189, 45, 44, 82, 229, 88, 101, 16, 166, 80, 230, 140, 75, 177, 228, 33, 248, 25, 103, 39, 195, 145, 66, 33, 37, 200, 2, 17, 0, 0, 0, 51, 73, 67, 205, 159, 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