Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dfcf9347f181c1e491977d27dd68be3d4efe6f7019d38250606839af73668a7

Tx prefix hash: 70183c42aa3aa88e389a8d4d5f44bf14342829a033474b106a33ba1f2ee2c3c8
Tx public key: 38f251cfd1ffcd0bc08e40e974963252dc34c26198501d0f00c0f09ad4703e63
Timestamp: 1755400613 Timestamp [UCT]: 2025-08-17 03:16:53 Age [y:d:h:m:s]: 00:047:15:58:06
Block: 1348228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33840 RingCT/type: yes/0
Extra: 0138f251cfd1ffcd0bc08e40e974963252dc34c26198501d0f00c0f09ad4703e63021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eebfe679c576fbd22a9d2e327f8fa9db8f85c04d7af061253d7b276e138e5b82 0.600000000000 1836151 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": 1348238, "vin": [ { "gen": { "height": 1348228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eebfe679c576fbd22a9d2e327f8fa9db8f85c04d7af061253d7b276e138e5b82" } } ], "extra": [ 1, 56, 242, 81, 207, 209, 255, 205, 11, 192, 142, 64, 233, 116, 150, 50, 82, 220, 52, 194, 97, 152, 80, 29, 15, 0, 192, 240, 154, 212, 112, 62, 99, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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