Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fae02b618d7ddf69cf286912f24fc0173869ff1366ac3d9a18b6a4953822457a

Tx prefix hash: 9969ef273648ad4fac136f0a0fc2a0056493061980a2a652b43f84f226153ef5
Tx public key: ac16d30cc3e2b36966383c4db256c8d34a4c3512cd8280ae831e6a8501f2cda1
Timestamp: 1627753445 Timestamp [UCT]: 2021-07-31 17:44:05 Age [y:d:h:m:s]: 04:096:14:00:30
Block: 304639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100007 RingCT/type: yes/0
Extra: 01ac16d30cc3e2b36966383c4db256c8d34a4c3512cd8280ae831e6a8501f2cda102110000002001f1e57f000000000000000000

1 output(s) for total of 60.062722664000 dcy

stealth address amount amount idx
00: 029f87ae793fb22b06d0177f38cfec27664022b71cbdb7175e2f9cec75e8bf40 60.062722664000 635582 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": 304649, "vin": [ { "gen": { "height": 304639 } } ], "vout": [ { "amount": 60062722664, "target": { "key": "029f87ae793fb22b06d0177f38cfec27664022b71cbdb7175e2f9cec75e8bf40" } } ], "extra": [ 1, 172, 22, 211, 12, 195, 226, 179, 105, 102, 56, 60, 77, 178, 86, 200, 211, 74, 76, 53, 18, 205, 130, 128, 174, 131, 30, 106, 133, 1, 242, 205, 161, 2, 17, 0, 0, 0, 32, 1, 241, 229, 127, 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