Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 947f4f7c4566f247d6171da1b7576e4bbd97a20f3916ec72a25ec9db526940a2

Tx prefix hash: c38eba94fb7ebf817ff0024c47eea8b55725ea3d5f8ef382787ca8f374b2089f
Tx public key: 7c63e8ac0613a875e79deb975b2223d912e7b060c69d5d39bdb6bca94e81575c
Timestamp: 1693998006 Timestamp [UCT]: 2023-09-06 11:00:06 Age [y:d:h:m:s]: 01:212:12:19:04
Block: 842169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412990 RingCT/type: yes/0
Extra: 017c63e8ac0613a875e79deb975b2223d912e7b060c69d5d39bdb6bca94e81575c021100000007faf35c9c000000000000000000

1 output(s) for total of 0.994362117000 dcy

stealth address amount amount idx
00: 57dcfbb71cb8fa429a09dcd243d0e1c26ad2ea813deff776bb03914349bfdc8f 0.994362117000 1295263 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": 842179, "vin": [ { "gen": { "height": 842169 } } ], "vout": [ { "amount": 994362117, "target": { "key": "57dcfbb71cb8fa429a09dcd243d0e1c26ad2ea813deff776bb03914349bfdc8f" } } ], "extra": [ 1, 124, 99, 232, 172, 6, 19, 168, 117, 231, 157, 235, 151, 91, 34, 35, 217, 18, 231, 176, 96, 198, 157, 93, 57, 189, 182, 188, 169, 78, 129, 87, 92, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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