Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fc3d81ecca2e68f02535463aa70dd319f7a7c9866b05a91732ed4dc128d0d01

Tx prefix hash: 28cdaa0fa09c800143c160b1cefcba693548145a400cdb93ab607c9fe4d71f84
Tx public key: dd7ec3b6889fb8fe4f5ed97115b3ada5e9da16e5231ad5ebb536b83779119e1b
Timestamp: 1701007177 Timestamp [UCT]: 2023-11-26 13:59:37 Age [y:d:h:m:s]: 01:095:09:15:21
Block: 900094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329304 RingCT/type: yes/0
Extra: 01dd7ec3b6889fb8fe4f5ed97115b3ada5e9da16e5231ad5ebb536b83779119e1b02110000000e75e3f0e9000000000000000000

1 output(s) for total of 0.639167839000 dcy

stealth address amount amount idx
00: c2b05057d2ba4c8db2c3b2418c81049f2fd9af46357b29d6a768aad424cdf108 0.639167839000 1356571 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": 900104, "vin": [ { "gen": { "height": 900094 } } ], "vout": [ { "amount": 639167839, "target": { "key": "c2b05057d2ba4c8db2c3b2418c81049f2fd9af46357b29d6a768aad424cdf108" } } ], "extra": [ 1, 221, 126, 195, 182, 136, 159, 184, 254, 79, 94, 217, 113, 21, 179, 173, 165, 233, 218, 22, 229, 35, 26, 213, 235, 181, 54, 184, 55, 121, 17, 158, 27, 2, 17, 0, 0, 0, 14, 117, 227, 240, 233, 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