Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 731d2974eef2ab89481705bb3e77b20f122b54750c854efbcf2b07a175cf85d1

Tx prefix hash: 7d8509e90355bd484e3a338e29c46ea6d4ba45c1ca5ee3700047d08488f681ab
Tx public key: 94d9c28fb3ad610b57eb00d3f2cb5c5084a15c2683f18386b23bb7e2a677ea1b
Timestamp: 1729081306 Timestamp [UCT]: 2024-10-16 12:21:46 Age [y:d:h:m:s]: 00:149:03:15:31
Block: 1132861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106356 RingCT/type: yes/0
Extra: 0194d9c28fb3ad610b57eb00d3f2cb5c5084a15c2683f18386b23bb7e2a677ea1b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c989607c3bc550a9760256b125d965d49992d19bf111e7ddd1f3debec00f7aa1 0.600000000000 1615876 of 15

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": 1132871, "vin": [ { "gen": { "height": 1132861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c989607c3bc550a9760256b125d965d49992d19bf111e7ddd1f3debec00f7aa1" } } ], "extra": [ 1, 148, 217, 194, 143, 179, 173, 97, 11, 87, 235, 0, 211, 242, 203, 92, 80, 132, 161, 92, 38, 131, 241, 131, 134, 178, 59, 183, 226, 166, 119, 234, 27, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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