Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91fcd0533a3fa28a1ca69f79f3b20d5bee48380c66a578a69797abf75ee6f6e8

Tx prefix hash: a460db87aaa581cf1083af56cb4890af41338282cece21573957eb9fed17a084
Tx public key: ff7b691d889f6027cc2ae0c0ed23a5124ea14ceb3bf024f147d2f033385f3131
Timestamp: 1695801657 Timestamp [UCT]: 2023-09-27 08:00:57 Age [y:d:h:m:s]: 01:118:11:43:42
Block: 857140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345922 RingCT/type: yes/0
Extra: 01ff7b691d889f6027cc2ae0c0ed23a5124ea14ceb3bf024f147d2f033385f313102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.887032251000 dcy

stealth address amount amount idx
00: bd182b59ec7f7f7898375528f3b707250bd3f4d68ec4dc7b2309763d5a559399 0.887032251000 1311248 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": 857150, "vin": [ { "gen": { "height": 857140 } } ], "vout": [ { "amount": 887032251, "target": { "key": "bd182b59ec7f7f7898375528f3b707250bd3f4d68ec4dc7b2309763d5a559399" } } ], "extra": [ 1, 255, 123, 105, 29, 136, 159, 96, 39, 204, 42, 224, 192, 237, 35, 165, 18, 78, 161, 76, 235, 59, 240, 36, 241, 71, 210, 240, 51, 56, 95, 49, 49, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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