Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f88567023dce76d27c4180eae1bfd509c74c6dea7ed739704b86d3918e15db

Tx prefix hash: 4e18fca0eca57bdb8bd1c2c91b1329b5c68d83ad944eafa714b8f71ee6310437
Tx public key: 643cdc4407a6269a1ccb2f2c4967680bf442473f94558803b2d73d0b3ee33516
Timestamp: 1749672705 Timestamp [UCT]: 2025-06-11 20:11:45 Age [y:d:h:m:s]: 00:159:01:53:40
Block: 1302984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111390 RingCT/type: yes/0
Extra: 01643cdc4407a6269a1ccb2f2c4967680bf442473f94558803b2d73d0b3ee335160211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76f7e8896d6cab4cfb87177664d06d6e39cc51c73d50c21f8c8b3152a882c66a 0.600000000000 1790559 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": 1302994, "vin": [ { "gen": { "height": 1302984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76f7e8896d6cab4cfb87177664d06d6e39cc51c73d50c21f8c8b3152a882c66a" } } ], "extra": [ 1, 100, 60, 220, 68, 7, 166, 38, 154, 28, 203, 47, 44, 73, 103, 104, 11, 244, 66, 71, 63, 148, 85, 136, 3, 178, 215, 61, 11, 62, 227, 53, 22, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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