Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 490e008215be6324730d2e93c996e7edcb1d786d3aa2531be9903742f304f106

Tx prefix hash: 4e9c597a9a13b01b3e22b80404cf30521e3d495b6ab85ed1d24a7dcde3d48bd7
Tx public key: ffeff49a9cdedd4bcdc8f8c11f8144e5c59417d55a4bf906ef21e713e590ee31
Timestamp: 1600882185 Timestamp [UCT]: 2020-09-23 17:29:45 Age [y:d:h:m:s]: 04:257:14:51:35
Block: 136362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163427 RingCT/type: yes/0
Extra: 01ffeff49a9cdedd4bcdc8f8c11f8144e5c59417d55a4bf906ef21e713e590ee3102110000006dfc4838fd000000000000000000

1 output(s) for total of 217.020973472000 dcy

stealth address amount amount idx
00: 7bdf40d53cafbacf46fe6bbee89be085d3556fcdd4a35f09e8f16508cafce6f0 217.020973472000 226887 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": 136372, "vin": [ { "gen": { "height": 136362 } } ], "vout": [ { "amount": 217020973472, "target": { "key": "7bdf40d53cafbacf46fe6bbee89be085d3556fcdd4a35f09e8f16508cafce6f0" } } ], "extra": [ 1, 255, 239, 244, 154, 156, 222, 221, 75, 205, 200, 248, 193, 31, 129, 68, 229, 197, 148, 23, 213, 90, 75, 249, 6, 239, 33, 231, 19, 229, 144, 238, 49, 2, 17, 0, 0, 0, 109, 252, 72, 56, 253, 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