Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb39e41b671420dda591bac22ec2493fbba7bfedfabd5ea1efca195ba08f77ef

Tx prefix hash: a71798b689f3edfad6a988f4dd89551c0ee83b1a8bfa73d95fd4faee81b0de84
Tx public key: 27ce0bdb89d521d373af57ae5aafd2a7a4871d7b71a54488aba4cf1f6e2db910
Timestamp: 1580977825 Timestamp [UCT]: 2020-02-06 08:30:25 Age [y:d:h:m:s]: 05:008:06:41:15
Block: 59746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157994 RingCT/type: yes/0
Extra: 0127ce0bdb89d521d373af57ae5aafd2a7a4871d7b71a54488aba4cf1f6e2db91002110000000103d36d11000000000000000000

1 output(s) for total of 389.078756288000 dcy

stealth address amount amount idx
00: 00b46e7c46e31fa286a4a7811b9f77bcb5482d1a40eb242af9c903c893c7d154 389.078756288000 110245 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": 59756, "vin": [ { "gen": { "height": 59746 } } ], "vout": [ { "amount": 389078756288, "target": { "key": "00b46e7c46e31fa286a4a7811b9f77bcb5482d1a40eb242af9c903c893c7d154" } } ], "extra": [ 1, 39, 206, 11, 219, 137, 213, 33, 211, 115, 175, 87, 174, 90, 175, 210, 167, 164, 135, 29, 123, 113, 165, 68, 136, 171, 164, 207, 31, 110, 45, 185, 16, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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