Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5564203d835754ada063b900b7ceb7af1dc6dc564d7bd71e0f1f7a10558d70a6

Tx prefix hash: 70df145dd467225bf906a77188216c5f70610815e158a0e97c04a5d8b2660c41
Tx public key: 73b2de545a92405b76e4162456b21063c9e12082fb8f7dd0657c2332a6639ffb
Timestamp: 1674014898 Timestamp [UCT]: 2023-01-18 04:08:18 Age [y:d:h:m:s]: 02:090:14:29:09
Block: 677178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586413 RingCT/type: yes/0
Extra: 0173b2de545a92405b76e4162456b21063c9e12082fb8f7dd0657c2332a6639ffb0211000000018b7b6602000000000000000000

1 output(s) for total of 3.501290317000 dcy

stealth address amount amount idx
00: 0f5aa3f7c26c3598bc8fc9316277503edfd720a8d8029a3ccde6cc4ef0ccff51 3.501290317000 1118945 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": 677188, "vin": [ { "gen": { "height": 677178 } } ], "vout": [ { "amount": 3501290317, "target": { "key": "0f5aa3f7c26c3598bc8fc9316277503edfd720a8d8029a3ccde6cc4ef0ccff51" } } ], "extra": [ 1, 115, 178, 222, 84, 90, 146, 64, 91, 118, 228, 22, 36, 86, 178, 16, 99, 201, 225, 32, 130, 251, 143, 125, 208, 101, 124, 35, 50, 166, 99, 159, 251, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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