Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f727387f2af27f201a5811a506fe7a1961cb23b9b93e1573990d50029c722e07

Tx prefix hash: 8cfd68387722c5ba4a704a31e2fb233537a7dccd292d43b663d26e1454ab1878
Tx public key: 4ef541a33dd258f4d6893881b41ee558a75d9b32eea3a9c57e6f8a7061cb91f3
Timestamp: 1702436096 Timestamp [UCT]: 2023-12-13 02:54:56 Age [y:d:h:m:s]: 01:038:14:14:03
Block: 911961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288887 RingCT/type: yes/0
Extra: 014ef541a33dd258f4d6893881b41ee558a75d9b32eea3a9c57e6f8a7061cb91f302110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57d7ec52322463bad6ec65da72364868d7a15147eb1cd57a91b810f023fa5c40 0.600000000000 1369179 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": 911971, "vin": [ { "gen": { "height": 911961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57d7ec52322463bad6ec65da72364868d7a15147eb1cd57a91b810f023fa5c40" } } ], "extra": [ 1, 78, 245, 65, 163, 61, 210, 88, 244, 214, 137, 56, 129, 180, 30, 229, 88, 167, 93, 155, 50, 238, 163, 169, 197, 126, 111, 138, 112, 97, 203, 145, 243, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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