Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 491b4893a847030cd4b540cbe796d0515c73e22eba22712117609997c6602d4a

Tx prefix hash: 128889a8ed8b86701cdc9cee483e3649e71fc0823b39d8b0f4468caaec84ab9a
Tx public key: 300d23c6983365832fcb817e4148be9569b59ccbae95b2a4af1fe6b3dca410fb
Timestamp: 1695493419 Timestamp [UCT]: 2023-09-23 18:23:39 Age [y:d:h:m:s]: 01:123:16:56:49
Block: 854573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349669 RingCT/type: yes/0
Extra: 01300d23c6983365832fcb817e4148be9569b59ccbae95b2a4af1fe6b3dca410fb0211000000024b8f5122000000000000000000

1 output(s) for total of 0.904575771000 dcy

stealth address amount amount idx
00: 2b273f71fc81bd85d85a0035576a489c69d2832f3e81e69d2d98a1f08ae39d95 0.904575771000 1308555 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": 854583, "vin": [ { "gen": { "height": 854573 } } ], "vout": [ { "amount": 904575771, "target": { "key": "2b273f71fc81bd85d85a0035576a489c69d2832f3e81e69d2d98a1f08ae39d95" } } ], "extra": [ 1, 48, 13, 35, 198, 152, 51, 101, 131, 47, 203, 129, 126, 65, 72, 190, 149, 105, 181, 156, 203, 174, 149, 178, 164, 175, 31, 230, 179, 220, 164, 16, 251, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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