Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c142ff5064bf75d79e44318341a2560ec20a7e02718cf8876d1deb68d0ef3f92

Tx prefix hash: 36d9fef91b4fb81a2c5d666841279b98a699cd855fe1a948be20f6e7f4b18d96
Tx public key: d7791682d11d08292baa260f03f87e1a040e8e73952c7ea1b243647d9569f742
Timestamp: 1732087318 Timestamp [UCT]: 2024-11-20 07:21:58 Age [y:d:h:m:s]: 01:001:12:34:17
Block: 1157664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259513 RingCT/type: yes/0
Extra: 01d7791682d11d08292baa260f03f87e1a040e8e73952c7ea1b243647d9569f7420211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbd8fedd73fea932c59c5ca81ee972e03b48f177e89a3b87b53714a60cde6535 0.600000000000 1643287 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": 1157674, "vin": [ { "gen": { "height": 1157664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbd8fedd73fea932c59c5ca81ee972e03b48f177e89a3b87b53714a60cde6535" } } ], "extra": [ 1, 215, 121, 22, 130, 209, 29, 8, 41, 43, 170, 38, 15, 3, 248, 126, 26, 4, 14, 142, 115, 149, 44, 126, 161, 178, 67, 100, 125, 149, 105, 247, 66, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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