Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04b1935bf9e8f0146e5cda90eecf810204e8d7ef5f2da1855b87db3d715447d8

Tx prefix hash: f5c6dffec7baa96935f216b96fba841a8b835cbe0c440e61881434708435e8a0
Tx public key: 3a3eb223a61e7c4ff194c1ea4b643b9f6833bfc1bd7c32c1654da6de741370f1
Timestamp: 1582035950 Timestamp [UCT]: 2020-02-18 14:25:50 Age [y:d:h:m:s]: 04:141:03:03:22
Block: 67546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 993100 RingCT/type: yes/0
Extra: 013a3eb223a61e7c4ff194c1ea4b643b9f6833bfc1bd7c32c1654da6de741370f10211000000084943cd9f000000000000000000

1 output(s) for total of 366.600345223000 dcy

stealth address amount amount idx
00: 7e8863f3c943647261fa1dad2efd65c3bedba860169a9a99091b6c901f83f304 366.600345223000 124415 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": 67556, "vin": [ { "gen": { "height": 67546 } } ], "vout": [ { "amount": 366600345223, "target": { "key": "7e8863f3c943647261fa1dad2efd65c3bedba860169a9a99091b6c901f83f304" } } ], "extra": [ 1, 58, 62, 178, 35, 166, 30, 124, 79, 241, 148, 193, 234, 75, 100, 59, 159, 104, 51, 191, 193, 189, 124, 50, 193, 101, 77, 166, 222, 116, 19, 112, 241, 2, 17, 0, 0, 0, 8, 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