Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 400e8bfc7bf5c9cc90f1f0dba266bc9011c45bb865b53ddd3c6a9f2c2739289e

Tx prefix hash: 4ffba03274f5fdfd69432a2d98647996d21ca1fb482b0bc84265bf6e6e995daa
Tx public key: cb74e67e42f21c7920e97d7eb9ebe67e2d9227b929a83199ebfa8d957802be39
Timestamp: 1702821205 Timestamp [UCT]: 2023-12-17 13:53:25 Age [y:d:h:m:s]: 01:329:02:18:38
Block: 915130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494067 RingCT/type: yes/0
Extra: 01cb74e67e42f21c7920e97d7eb9ebe67e2d9227b929a83199ebfa8d957802be3902110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a020f7ca69fbcec5b5f862617a6be3b0db76dd800a06185b8752d7d3e0c91211 0.600000000000 1372516 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": 915140, "vin": [ { "gen": { "height": 915130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a020f7ca69fbcec5b5f862617a6be3b0db76dd800a06185b8752d7d3e0c91211" } } ], "extra": [ 1, 203, 116, 230, 126, 66, 242, 28, 121, 32, 233, 125, 126, 185, 235, 230, 126, 45, 146, 39, 185, 41, 168, 49, 153, 235, 250, 141, 149, 120, 2, 190, 57, 2, 17, 0, 0, 0, 4, 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