Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b11940d4bd3b6f3c2d3306b4815630696a534c9db40315dafb56e15d06460fdf

Tx prefix hash: 76c2f7d1dd84f85d696200748bab4f873405083200b825cfc2aa2626900cc3ae
Tx public key: ee2146a69ef7e5fb34c875100178daa5f4f81d265266d92c865cfae6f4093fc7
Timestamp: 1582642295 Timestamp [UCT]: 2020-02-25 14:51:35 Age [y:d:h:m:s]: 04:362:19:51:36
Block: 72253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151757 RingCT/type: yes/0
Extra: 01ee2146a69ef7e5fb34c875100178daa5f4f81d265266d92c865cfae6f4093fc70211000000010aca7173000000000000000000

1 output(s) for total of 353.668693217000 dcy

stealth address amount amount idx
00: 8d54b721a2a6c7fac8ebef42f80ee17088a10190413ee58d84f049489fd1f72c 353.668693217000 133432 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": 72263, "vin": [ { "gen": { "height": 72253 } } ], "vout": [ { "amount": 353668693217, "target": { "key": "8d54b721a2a6c7fac8ebef42f80ee17088a10190413ee58d84f049489fd1f72c" } } ], "extra": [ 1, 238, 33, 70, 166, 158, 247, 229, 251, 52, 200, 117, 16, 1, 120, 218, 165, 244, 248, 29, 38, 82, 102, 217, 44, 134, 92, 250, 230, 244, 9, 63, 199, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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