Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe51078f48b84efedc4dd19d1e6a314923ba65ba92a66c006f5b3ffd53b2c6bc

Tx prefix hash: 637463ff44d1b9f3dd02168050f9330010441dcc2135be40412f89f15a22c550
Tx public key: 2478047c1b8d21166b1216c990535ef77a46a9c803a9e9fdb84271b3f0bdcb93
Timestamp: 1718919986 Timestamp [UCT]: 2024-06-20 21:46:26 Age [y:d:h:m:s]: 00:287:15:47:46
Block: 1048591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205566 RingCT/type: yes/0
Extra: 012478047c1b8d21166b1216c990535ef77a46a9c803a9e9fdb84271b3f0bdcb930211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41ab7e59dcd3e82091858d7c740780edc36b4e062e94f20a80c451c61aecedfe 0.600000000000 1518676 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": 1048601, "vin": [ { "gen": { "height": 1048591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41ab7e59dcd3e82091858d7c740780edc36b4e062e94f20a80c451c61aecedfe" } } ], "extra": [ 1, 36, 120, 4, 124, 27, 141, 33, 22, 107, 18, 22, 201, 144, 83, 94, 247, 122, 70, 169, 200, 3, 169, 233, 253, 184, 66, 113, 179, 240, 189, 203, 147, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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