Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebb4e341bbda16375bffc138b1432d62ec764b27bdc713d81f073720139904f9

Tx prefix hash: 73840a9ad996809ea5ba7cb0bc669de3f5ddfa38c2e4d676c4506b03d26eb357
Tx public key: bd9698c1de0296bc7fe415fb389c7a314edd8a2678cc1f784ea6b99efb9044ea
Timestamp: 1610177028 Timestamp [UCT]: 2021-01-09 07:23:48 Age [y:d:h:m:s]: 03:314:10:21:29
Block: 176414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 980120 RingCT/type: yes/0
Extra: 01bd9698c1de0296bc7fe415fb389c7a314edd8a2678cc1f784ea6b99efb9044ea02110000001f4ea414e5000000000000000000

1 output(s) for total of 159.759922599000 dcy

stealth address amount amount idx
00: bdb457137f9d892a8bbd0c3bb3fe086cbcdf414708b07cba7c9f5fdf762087be 159.759922599000 337924 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": 176424, "vin": [ { "gen": { "height": 176414 } } ], "vout": [ { "amount": 159759922599, "target": { "key": "bdb457137f9d892a8bbd0c3bb3fe086cbcdf414708b07cba7c9f5fdf762087be" } } ], "extra": [ 1, 189, 150, 152, 193, 222, 2, 150, 188, 127, 228, 21, 251, 56, 156, 122, 49, 78, 221, 138, 38, 120, 204, 31, 120, 78, 166, 185, 158, 251, 144, 68, 234, 2, 17, 0, 0, 0, 31, 78, 164, 20, 229, 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