Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16f7624156f203319fd8674c66d33b347834e45728ae14ef412cf2e545df2bb1

Tx prefix hash: 6178708f98f6675325373ec6bdd4698eb2a58f83a3447ae5f4cd45ed4ecd5e5a
Tx public key: 7a10052fb3becf71ddce67c962675fe5e4ef829813e2f8f33e9ef3c5f4872189
Timestamp: 1673026999 Timestamp [UCT]: 2023-01-06 17:43:19 Age [y:d:h:m:s]: 02:025:19:54:41
Block: 668984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540120 RingCT/type: yes/0
Extra: 017a10052fb3becf71ddce67c962675fe5e4ef829813e2f8f33e9ef3c5f48721890211000000017e406890000000000000000000

1 output(s) for total of 3.727161902000 dcy

stealth address amount amount idx
00: 0548b76cf3d2c103595327b6e796d95129f8da00c9c6a1bfbb2170a689c4a635 3.727161902000 1110265 of 0

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": 668994, "vin": [ { "gen": { "height": 668984 } } ], "vout": [ { "amount": 3727161902, "target": { "key": "0548b76cf3d2c103595327b6e796d95129f8da00c9c6a1bfbb2170a689c4a635" } } ], "extra": [ 1, 122, 16, 5, 47, 179, 190, 207, 113, 221, 206, 103, 201, 98, 103, 95, 229, 228, 239, 130, 152, 19, 226, 248, 243, 62, 158, 243, 197, 244, 135, 33, 137, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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